This stack is designed for anyone developing Hypercard stacks. It includes public domain, freeware, and shareware XFCNs*, XCMDs*, HyperTalk functions and useful script segments. It is a user supported effort and will constantly be growing. The basic idea is to collect all the useful resources* a Hypercard developer needs into one place, making the development process much easier and faster. This stack is designed as a learning tool. Nothing is protected or hidden from the user. Tear into the scripts until you understand what they do. Play around with the XCMDs and XFCNs.
««How it works»»
This copy of the stack you are reading is the main library* for all the information. It is distributed through electronic bulletin boards, users groups, and other public domain sources*. About every 3 months it is updated to include all the latest resources, ideas & techniques that may be useful to a Hypercard developer.
You may add as many cards as you like to this stack without affecting its operation. All the indexes will automatically be updated for you. Just be certain not to rename or delete any of the backgrounds. For a larger distribution of ideas, it would be better if you send new script segments, functions, XFCNS, & XCMDs to us for inclusion in stack updates. Developer Stack has subscribers & supporters worldwide.
««What you have to do»»
The only way this stack will succeed as a useful resource for developers is if everyone contributes. It's easy to do, and you even get something in return. If you have written any XFCNs, XCMDs, functions, scripts, or other HyperCard related items that you have found useful, send it to us (more details below). In return, you will receive the latest version of the Developer Stack, and a warm feeling inside from being a contributing member of the Macintosh* and Hypercard community. Hypercard has made developers out of many people who would have never thought of programming efore. Now the Developer Stack is here to make distribution of all the great new ideas and techniques simple.
If you use the Developer Stack in developing any stacks to be released, please include the following credit somewhere in the stack:
ΓÇóΓÇóΓÇó
Developed with the aid of the Developer Stack.
To receive the latest version of the Developer Stack, send $10.00 to:
AnalytX
Box 388
Southampton, PA 18966
ΓÇóΓÇóΓÇó
««Credits»»
I have tried to give credit for everything included in the stack. There are a few items that have gone without credit because I don't know where they originally came from. If you recognize any of them, and can attribute them to the correct person, please let me know. Anything sent for inclusion in the stack will be credited to the person who created it. (You too can become famous and people will be able to talk about you behind your back, if you would only contribute.)
««New issues»»
With all the action going on in the Hypercard community we can all benefit from new ideas and resources*, collected into one place. We will take contributions from any source with the following conditions:
1) If you send something to be included in the stack, it should be debugged and ready to go.
If it includes any scripts, they should be well commented, and have a header giving credit to yourself. Shareware items will be included in the stack, with the appropriate notations.
2) If you send something to be included in the stack, and want to receive the latest version of the Developer Stack, you MUST include a self-addressed stamped envelope. If you don't, you won't get your disk back with the new Developer Stack issue.
3) If you have any ideas or comments about the stack, and where it should go (future direction-wise, not physically), LET US KNOW! Don't keep your ideas to yourself.
We would like to see this grow into a useful tool for ALL Hypercard users, not just the experts. While this stack has been tested thoroughly, there still may be some bugs*. If you find any PUHLEASE let us know. Send mail (USPS or electronic).
4) We cannot guarantee that any specific contribution will be included in an update of the stack. However, any that are included will be given full credit as to their original source.
««How to reach us»»
US MAIL:
Steve Drazga*
AnalytX
Box 388
Southampton, PA 18966
(215) 750-0792
GEnie:
S.DRAZGA
Compuserve:
76530,1107
««What you should send as a contributor»»
1) A disk with your contribution. Since it probably won't fill up the entire disk, you can also include some stacks, sounds (love those digitized sounds), or any other neat programs you have.
2) A self-addressed stamped envelope - if you want your disk returned with a copy of the latest update of the Developer Stack.
3) A note telling me what Hypercard is in 15 words or less (HA!).
4) $100,000* in small bills, or your suggestions for the continuing growth of this stack as a developers' tool, if you happen to be low on cash.
««What if you just like to watch?»»
ΓÇóYou say you haven't got the hang of Hypercard yet.
ΓÇóYou don't think you have anything that would interest other HC users?
ΓÇóYou say you're still having trouble putting the disk in the right side up.
ΓÇóYou say you can't get the upgrades from a users group because you wouldn't want to belong to any group that would have you as a member.
ΓÇóMaybe you can't download the latest version because you think telecommunication is calling you mother-in-law.
No Problem. You can get the latest version of the Developer Stack by sending $10
(US funds, please) to the address above. Make sure you indicate what version you have so we don't send you a duplicate copy. You can also subscribe to the Developer Stack for a year for just $35. You will receive the next four issues of the Developer Stack. Make all checks payable to AnalytX. If you would like it shipped overseas*, please add $1.50 per issue as a bonus for our deserving postal employees.
I will try to answer any questions you send in. However, if you don't include a self addressed stamped envelope with your questions, don't expect an answer.
-- part contents for card part 6
----- text -----
Registered Trademark of Apple Computer. (He made me say it, Ma!)
External Function resources, used to extend the usefulness of HC.
-- part contents for card part 8
----- text -----
External Command resources, used to extend the usefulness of HC.
-- part contents for card part 9
----- text -----
Since it is a repository for alot of different types of information on HC, I call it a library. Besides, who wrote this stack, anyway?
-- part contents for card part 10
----- text -----
This is neat. It will automatically copy all the new cards and resources into the right places in the Developers stack with just a click of a button.
-- part contents for card part 11
----- text -----
Registered trademark of Apple Computer. Hey, wait a minute. Angus Macintosh might have something to say about that. (I wonder how that goes over in Scotland -- "Yeah, I just bought a Macintosh").
-- part contents for card part 12
----- text -----
Steve Drazga...
Wait a minute, isn't he the guy that is putting out the Developer stack? What a sport!
-- part contents for card part 13
----- text -----
American dollars or Japanese yen only. None of that Canadian stuff, eh.
-- part contents for card part 14
----- text -----
I'm not talking about the kind of resources you move with resedit. I'm talking about the kind of resources you use to make life easier for yourself. A remote control is this kind of a resource.
-- part contents for card part 15
----- text -----
If lots of people send in their tricks and techniques, it may come out at two week intervals. If everyone sits on their backsides staring at 9 point type on a computer screen like, for example, YOU, then it may come out only once a month or so. The point is, there are lots of people doing lots of Hypercard programming. We just have to get together.
-- part contents for card part 16
----- text -----
"Ha! You bought a Macintosh?! Isn't that cute. It's got a cute little screen. It must be fun to play with. And look at those cute little pictures. I guess you have to be pretty stupid to need little pictures, huh..."
Anybody who was part of the Macintosh front lines, in 1984 and 1985 remembers that. Guess they finally realized that IBM users are just as stupid as Mac users, with PS/2 et al.
-- part contents for card part 17
----- text -----
AnalytX is a Macintosh consulting & software development firm specializing in Hypercard applications & training. For more information custom stacks, XCMDs, or other Macintosh consulting needs, give us a call at (215) 750-0792.
-- part contents for card part 2
----- text -----
Innovative Hypercard Stackware
-- part contents for card part 19
----- text -----
We can not guarantee future issues of Developer Stack will be distributed through 'freeware' channels. To be assured of receiving information on new issues, make sure you are on our mailing list. The only guaranteed method of getting the next issue is to order it directly ($10, cheap) or send a contribution to be included in the stack.
-- part contents for card part 20
----- text -----
Definition - Bugs:
1) Unadvertised features.
2) Unimplemented future enhancements.
3) User oriented interface discrepancies.
4) Bugs? What bugs.
5) Microsoft Word 3.0
6) System 6.0
-- part contents for card part 21
----- text -----
Just in case you are interested, we do consider Canada and Mexico to be overseas. While technically they are part of the North American continent, our postal employees don't cross the border (too cold to walk up north, no decent water to drink down south) so you're stuck paying the extra $1.50 too.
